pepe/ALLSHIFT
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ALLSHIFT/docs/07-team-and-operations/interview-questions.md
pepe 72dd781dbc Organize documentation into docs/ and superseded/ 
Audit every document in the repository, convert the non-markdown ones into
markdown reports, and split current documentation from outdated material.

docs/ — 31 markdown documents in seven numbered sections. Twenty are new
reports generated from .docx / .pdf / .xlsx / .mlx / .m sources that were
previously unreadable in the browser and undiffable in git. Each report
carries a provenance block (source path, format, MD5) and links back to its
original; all 13 recorded checksums verify against the files on disk.
Machine-extraction losses (PDF table column interleaving, Word OMML
equations, embedded figures) are called out explicitly rather than silently
smoothed over.

superseded/ — outdated material with a documented reason per entry:
two byte-identical ClickUp re-exports, an older revision of the BIDMC/UCSD
energy-flow doc (the retained copy adds the SoC Violation Rate KPI), a
duplicate of Shift input data.docx, the May 2026 simulation plan, the
root PV+Battery.md now covered by a fuller report, GitHub's stock
demo-repository template, and a zero-byte placeholder. Its README also
records what was deliberately NOT retired and why — the "Old Frameworks"
and "Old Simulations" folders hold unique Simulink revisions, and
"Big Ugly Folder" holds the only copy of framework revision 1.3.

Findings worth flagging, all documented in the reports:
- Simulink lineage recovered from each .slx's internal coreProperties.xml
  revision counter. The current model is
  Current Framework/Bobert0206_Initial_Simulation_Framework.slx (rev 2.7);
  the top-level copy is rev 1.3, five revisions behind.
- Simulations/Constants.m is a truncated byte-prefix of the Current
  Framework copy, silently missing H2_leak, H2_cap and E_H2_vol_h.
- The PEM electrolyser and fuel cell are unmodified MathWorks Simscape
  examples still at vendor defaults; the "10x bigger" sizing TODO recorded
  in Constants.m was never carried out.
- controller-claude.m does not compile — undefined P_Electro_max, outputs
  unassigned on several paths.
- The specification set uses two incompatible variable naming conventions
  and disagrees on action-space size (5 vs 16).
- MA_hourly_load.csv (13.7 MB) is the same 35,040 rows as 89993-0.parquet
  (2.4 MB).
- Clinical data is the MIMIC-IV *demo* (ODbL, 100 patients), not full
  MIMIC-IV — redistributable, but the licence and citation are unrecorded.

Housekeeping: untrack 21 Simulink build artefacts (slprj/, *.slxc) and add
ignore rules for them. Root README rewritten around the new layout.

Recruitment notes naming individual candidates are excluded from version
control via .gitignore rather than committed; the generic question template
is kept in docs/07-team-and-operations/.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-25 21:20:33 -07:00

2 KiB
Raw Blame History

Interview Questions

  1. Can you briefly introduce yourself and your academic background - name, age, study, year of study, previous education, etc.
  2. What attracted you to Team SHIFT and this project specifically?
  3. What do you hope to gain from joining the team?
  4. What does your course load look like/How many hours per week can you realistically commit?
  5. Are you planning any exchanges, internships, or heavy semesters that may affect your availability?
  6. What motivates you more: technical challenges, real-world impact, teamwork, or something else?

A. For Technical Cluster Candidates:

Questions:

  1. What technical skills do you feel most confident in? (Python, ML, control, simulations, electronics, energy systems…)
  2. Have you worked with machine learning, reinforcement learning, or control systems before?
  3. How comfortable are you with learning new tools on your own?
  4. Do you prefer theoretical modelling, coding, hands-on engineering tasks, or data analysis?
  • Explain how you would design a simple forecasting model for solar energy or energy demand.
  • Explain what an energy management system is in your own words.

B. For Business & Economics Candidates:

Questions:

  1. Have you worked with business modelling, financial analysis, or market research before?
  2. What interests you about the hydrogen and AI–energy sector?
  3. How would you estimate the economic value of an AI-based energy management system for a hospital?
  4. How comfortable are you with presenting findings to technical team members?

C. For PR & Communications Candidates:

Questions:

  1. What experience do you have in PR, branding, or social media management?
  2. What would you improve about our current communication or website?
  3. Are you confident producing content (graphics, articles, videos, LinkedIn posts)?
  4. Mention that they will have a lot of control and creative freedom in PR and designing things Then say thank you for your time, do you have any questions for us, etc.